Perhaps you should add both beans .jar files to a single .ear file. JBoss puts all jar files contained it the ear in the classpath for the application.
As you describe your EJB deployment as being two
jar files, it is important to view deployed
jar, war, and ear files as *separate* deployment
units. As such they would have no class loader
visibility across the deployment units.
If there are any dependencies, you must include
the Home and Remote interfaces of the dependent
component. That way you have visibility even
if the dependent component is deployed in another
It is an easy trap to view a JBoss app server
install as an island. It might not be. It may be
part of a federation of app servers running on
different machines. In this very possible scenario
class loader visibility across deployment units
on seperate machines is impossible.
As Marcus, pointed out, if you have close coupling
where two components always occur together, then it
makes sense to deploy them togther in the same
Just my thoughts.