CDI 1.1 is humming along nicely and recently released it's public review draft. Although it's just a point release, CDI 1.1 actually has a lot in it. Some the changes include:

• The CDI class, which provides programmatic access to CDI facilities from outside a managed bean
• Ability to veto beans declaratively using @Vetoed
• Conversations in Servlet requests
• Application lifecycle events in Java EE
• Injection of Bean metadata into bean instances
• Programmatic access to a container provided Producer, InjectionTarget, AnnotatedType
• Ability to override attributes of a Bean via BeanAttributes
• Ability to process modules via ProcessModule
• Ability to wrap the InjectionPoint
• Honor WEB-INF/classes/META-INF/beans.xml to activate WEB-INF/classes in a bean archive
• Global ordering and enablement of interceptors and decorators
• Global selection of alternatives
• @New deprecated
• Clarify interceptors and decorators must be implemented using proxying
• Allow multiple annotated types per Java class
• Allow Extensions to specify the annotations that they are interested in

The CDI 1.1 expert group has a number of open issues that they would like immediate feedback on. These include critical issues like bean visibility, startup events and restricting CDI scans. Read the details here and let your voice be heard!