Spec must be clear about the fact that JAX-RS on Java EE enforces underlying Servlets 3.0 and Autoconfiguration

The JAX-RS 2.0 spec should clearly say that when deploying to a Java EE container independent of the actual technology it is using no configuration is required by the application programmer or developer, but an auto-scanning mechanism MUST be applied by the Java EE container (even if that one is NOT based on Servlet 3.0). That is the only way to guarantee WORA in Java EE, since Java EE enforces Servlets, but does not enforce JAX-RS to base on Servlets. The spec currently only says how to deploy on Servlets but does not mandate Servlets itself. This unfortunately leaves room for implementations that are provided by Java EE containers, but that will not base on Servlets.
#### Environment
Jersey 2.0 M08-1, JAX-RS 2.0 M12, JRE 1.7.0_07
#### Affected Versions
[2.1]