I'm running into a similar issue where the remoting class loader (org.jboss.remoting.loading.RemotingClassLoader) logic to ask the parent class loader before the user class loader is reversing the class loading policy of the javaee app client container. This results in inconsistent classes as bean interfaces are being loaded twice. At a minimum, there needs to be a parent first flag that allows the user class loader to be tried first. The description of the fix for JBREM-962 I see is too specific to the jboss4x class loader architecture, so I'm going to create a new issue for 2.4.0.GA. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167417#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...