There are certain bits in the specification that have been carried over as deprecated legacy for years.
I think for future versions we can easily shake them off.

I discovered the following deprecated parts that I think we can remove:

• @New qualifier
  • Deprecated since CDI 1.1 and replaced by @Dependent
• Bean.isNullable() method
  • Deprecated since CDI 1.1
• BeanManager.fireEvent() method
  • Deprecated since CDI 2.0 and replaced by BeanManager.getEvent()
• BeanManager.createInjectionTarget(AnnotatedType) method
  • Deprecated since CDI 1.1 and replaced by BeanManager.getInjectionTargetFactory(AnnotatedType)
• BeforeBeanDiscovery.addAnnotatedType(AnnotatedType) method
  • Deprecated since CDI 1.1 and replaced by BeforeBeanDiscovery.addAnnotatedType(AnnotatedType, String)
• Remove the notion of a mandatory configuration switch for all container to support different understanding of missing beans.xml
  • This behavior change exists ever since CDI 1.1
  • Stated in the following part of specification - https://jakarta.ee/specifications/cdi/2.0/cdi-spec-2.0.html#bean_archive
  • For compatibility with Contexts and Dependency 1.0, products must contain an option to cause an archive to be ignored by the container when no beans.xml is present.

Obviously, for all of the above changes might be needed in both, API and specification text.