I have an ear file with inside a jar file with an ejb.
Use the CLI to deploy with:
> deploy simpleejb3.ear

In the console log:

12:22:42,130 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "simpleejb3.ear"
12:22:42,174 INFO [org.jboss.as.server.deployment] (MSC service thread 1-16) JBAS015876: Starting deployment of "simpleejb3-ejb.jar"
12:22:42,293 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-5) JNDI bindings for session bean named sbean in deployment unit subdeployment "simpleejb3-ejb.jar" of deployment "simpleejb3.ear" are as follows:

java:global/simpleejb3/simpleejb3-ejb/sbean!tf.sbeanLocal
java:app/simpleejb3-ejb/sbean!tf.sbeanLocal
java:module/sbean!tf.sbeanLocal
java:global/simpleejb3/simpleejb3-ejb/sbean!tf.sbeanRemote
java:app/simpleejb3-ejb/sbean!tf.sbeanRemote
java:module/sbean!tf.sbeanRemote
java:jboss/exported/simpleejb3/simpleejb3-ejb/sbean!tf.sbeanRemote

and the bean will work.

Now undeploy fully (+ restarted) and deploy again with:

> deploy simpleejb3.ear --name=b

and the log :

12:23:41,300 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "b"
12:23:41,431 INFO [org.jboss.as.osgi] (MSC service thread 1-4) JBAS011907: Register module: Module "deployment.b:main" from Service Module Loader
12:23:41,598 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "b"

A test showed that the EJB was indeed not deployed/accessible.