The issue is classes loaded by the jbossweb.sar class loader interacting with factories that make use of the tccl need to reset the tccl to avoid mixing classes visible to the app. Part of the issue is that the war deployment is initiating the creation of the war application classes in its start and this is what the tccl is set to the war deployment class loader. Finishing the migration to mc beans should improve this. The parsing of the metadata should also have happened before the application is being started. The best workaround in the meantime does look to be setting/clearing the tccl as proposed by rodos77. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251359#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...