Thinking more about this, the conflict can arise even when there are 2 beans with the same classname (but different package names) in the same jar. Ex: MyApp.ear/Single.jar package org.myapp.business; | | @Stateless | public class ManagerBean implements org.myapp.business.Manager { | | } package org.myapp.persistence; | | @Stateless | public class ManagerBean implements org.myapp.persistence.Manager { | | } View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183030#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...