The obvious fix would be to add some mergeScope() methods to ScopeInfo which would know to avoid the hack that converts the class name -> class. The merging of the mutable scope shouldn't be happening. Its a recipe for all sorts of confusion if DefaultScopeBuilder and KernelScopeInfo disagree on what that should be. DefaultScopeBuilder (or some deployer that sets the mutable scope on the deployment unit) should be the only authority for that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4185137#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...