OK, yes. I had to do something similar. Both of my ear files had all of the ejb-jars deployed from the lib directory. Moving all of the ejb-jars in one of them to the root of the ear file resolved the issue.
Reply to this message by going to Community
Start a new discussion in JNDI and Naming at Community