It looks like our EE managed bean support doesn't require the jakarta.annotation.ManagedBean annotation type to be visible on the classpath. EE 11 removes the jakarta.annotation.ManagedBean type, and removes support for EE managed beans, but if our impl doesn't actually require the type we might be able to improve compatibility and ease migration by continuing to support EE < 11 managed beans in an EE 11+ server.

This would likely need some sort of configuration aspect, e.g. a 'managed-bean-support-attribute' with values like:

• spec-compliant – allow managed beans if the annotation type is present; fail the deployment if they are used and the annotation is not present.
• forgiving – allow managed bean if the annotation type is present, log at INFO but otherwise ignore managed beans if they are used and the annotation is not present
• migration – allow managed beans regardless of the presence of the annotation type. Log at WARN if the annotation type is not present.