No error condition was raised when managed bean contained a reference to another bean with a potentially shorter scope than what the bean was configured for.

Acording to the spec (section 5.3.1.3, p5-11):

"It is an error for a managed bean created through this facility to have a property
that points at an object stored in a scope with a (potentially) shorter life span.
Specifically, this means, for an object created with the specified <managed-beanscope>,
then <value> evaluations can only point at created objects with the
specified managed bean scope:

• none – none
• application – none, application
• session – none, application, session
• request – none, application, session, request"

I guess the ManagedBeanFactory should throw a FacesException in that case.

(managedBeanScopedReferencesTest)