Still a problem in weld-se-1.1.9.Final.

slf4j-api should be a dependency of weld-se. It should in no case be shaded into the weld-se jars.
Because it's shaded, maven doesn't see the conflict when you combine a slf4j-api dependency with a weld-se dependency.
As a result, you get messages like this in your console:

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/gdesmet/.m2/repository/ch/qos/logback/logback-classic/1.0.0/logback-classic-1.0.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/gdesmet/.m2/repository/org/jboss/weld/se/weld-se/1.1.7.Final/weld-se-1.1.7.Final.jar!/org/slf4j/impl/StaticLoggerBinder.class] // BAD weld-se is not a logging implementation!

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira