(OpenEJB) Local and remote ejb access inside eclipse plugin
===

I am trying to expose beans running in an OpenEJB container(running in a plugin) to other plugins AND to remote clients. The other plugins are covered with a tutorial I found. The beans communicate locally via the local interface... fine. The problem is then getting another process to communicate with the container also. The container exposes the bean when the @remote annotation is added but the problem is that none of the services on the container start up. It turns out that services on the container (of which ejbd is one) is scanned and discovered only if the service's jar is on the classpath. As I understand it this classpath scanning is forbidden in the plugin architecture as it is built on OSGi. 

Are my assertions correct?

Is there a way to force the ejbd service to start as a part of the activation of the plugin?

OR

Is there a way to tell OpenEJB to look somewhere that can be specified with the plugin manifest to look for the service jars?