is there any specific reason you need the jar file to live in a lib directory?
why not just place the AdminClient.jar at the same level w/ the ejb-app.jar and modify the Class-Path in the manifest file to look for the jar like this:
You are editing the wrong manifest file. Use the manifest inside the ejb-app.jar file and it will work.
lib/AdminClient.jar should work
otherwise, decalre AdminClient.jar as a Java module and it will be "deployed" by jobss
one of the beauties of the JBoss classloaders is that if that jar is visible ANYWHERE then the system will pick it up.
one of the things that may be throwing you off is that the jar doesn't get picked up before the EJB.
Several ways. putting stuff in lib/ will make sure it is picked up first before everything else. Otherwise do russian doll packaging (put your jar in the ejb jar and it will be deployed first).