We are currently in the process of evaluating the migration of our application from JBoss 4.x to JBoss 5.1.0.GA and are experiencing what seems to be the same issue. The only way we have been able to get around this problem is to disable the WarClassLoaderDeployer (by commenting it out in war-deployers-jboss-beans.xml), however, this is not an ideal workaround. Any help would be appreciated. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250182#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...