title: What's the point of using @Scoped with EJBs?
body: <p>Usually I'm using <code>@RequestScoped</code> or <code>@SessionScoped</code> (from <code>javax.enterprise.context</code>) to inject objects (for instance in faces beans) using <code>@Inject</code>.
  I am also using EJBs. As I understood, a set of stateless EJB copies (pool) is used to be injected to objects. The reason there are many copies is to ensure one instance of EJB isn't accessed concurrently. When speaking about stateful EJBs (again as I understood), one instance of such is bound to concrete injection point. And they are injected using <code>@EJB</code> (the stateless ones too).</p>
  
  <p><strong>Frequently I can see on the web examples of using <code>@Stateless</code> or <code>@Stateful</code> in conjunction with <code>@Scoped</code>. What is the meaning of them?</strong> </p>
  
  <p><strong>Edit:</strong> (trying to clarify as no one responded to this moment):</p>
  
  <p>I'm especially interested whether such scoped annotations change anyhow (and if they - how) moment of creation of EJB's instance. 
  For my understanding: if I have, <code>@EJB</code> annotated field, object of proper class is injected there. If such EJB is stateless, container simply take free instance from the pool of pre-created instances. Pool can be resized if necessary. It is stateless, because object isn't guaranteed to be preserved across method calls of our class (i.e. class which has field containing reference to EJB).</p>
  
  <p>We can also use stateful EJB and in that case one instance is preserved during method calls. As I think, it will be simply injected once per object creation. (There is also singleton EJB, which is shared between all objects).</p>
  
  <p>I can't find the purpose of @Scoped annotations for EJB here.</p>
  
  <p><strong>Edit 2:</strong></p>
  
  <p>One can use such combination of annotations if class is to be injected via EJB and DI (by <code>@Inject</code>) mechanisms. This is rather, however, special case and not elegant. I am asking if you know any other reasons.</p>
  
  <p><strong>Edit 3:</strong>
  Please see my comment under arjan's answer.</p>