We should create a concept about what to do with the JSF managed bean mechanism with regard to CDI (JSR-299).
Since CDI was created to handle JSF's managed bean mechanism better in the first place (remember: "webbeans") and since it is being used a lot already to handle managed beans in JSF web applications, we should think about what to do with JSF's own managed bean mechanism.
The are some spec-issues in this tracker refering to improvements of the JSF managed bean mechanism, like e.g. new scopes (I saw @AccesScoped and something about @FlashScoped). However, we should think about if improving this mechanism is the right choice.
Maybe a better idea is to deprecate JSF's managed bean mechanism (like we deprecated JSP support - meaning that we still support it, but do not create new features for it) and automatically map JSF managed bean annotations to CDI annotations at startup, if CDI is available (like MyFaces CODI or JBoss Seam are supporting already).
@javax.faces.bean.ManagedBean --> @javax.inject.Named
@javax.faces.bean.SessionScoped --> @javax.enterprise.context.SessionScoped
Also see  for a feature description.
IMO you should not use JSF 2.x without CDI (at least if you're doing more than hello world).