Business logic: EJB vs OSGi declarative services
<p>I know that EJB is de facto standard in enterprise applications for business logic. However, osgi declarative services can do a lot of things which EJB do. Both are managed by container, both can be used as singleton, both can be used with CDI. The differences which I found are: </p>

<ol>
<li>EJB has already RMI mechanism but DS don't.</li>
<li>EJB has thread pool but DS don't</li>
<li>DS can require only OSGi but EJB requires JavaEE container (for example if we develop standalone application using JavaEE container will be difficult. Because it will either lead to performance overhead or to necessity to extract EJB container from JavaEE implementation (exm glassfish).</li>
</ol>

<p>What are other important advantages of EJB explaining its using as standard?</p>

<p><strong>EDIT:</strong><br>
The reason why I asked this question is the following - we want to develop some business logic which can be used both for SE and EE platform. That's why DS seem to be a better solution. However EJB and DS are two universes and we are afraid of missing something important.</p>