Yes, having the ejb jar file appear both in the ear and the war will cause a problem. The ejb will be created using the class definition from the jar in the ear, and then when code in the war attempts to access it, the jar in the war will be used for the class definition, and those are not the same because of the different classloaders used. Removing the ejb jar from the war should solve the issue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170433#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...