I think
you should look about
this.
Edited:
Hmm, you changed the question, so do I my answer. :-)
For sure, you just have to be aware the price to pay by willing this. Every EJB exposed to your clients will have to be remote or web services, so you're gonna pay the overhead. To achieve this in the most straight forward way I do is to include a jndi.properties on your classpath, then you'll use the server specified there instead the local one.
You can also rely on the low-level JNDI lookup / Service Locator, but it's not recommended. Try to keep away as much as possible if you want to avoid complexity and very tightly coupling. Let the container, annotations and deployment descriptor elements do the heavy / monkey job for you and be happy.
You can spare the time that you'll earn doing this paying a beer for us here on the bar, :P
Feel free to ask me anything!
www.BlackBeltFactory.com/ui#!/ref=jmotta, SCJP 6, OCWCD JEE5, OCE EJB JEE6