code: public void cleanupFinalBeanManagers(@Observes AfterDeploymentValidation adv)
      {
          for (BeanManagerInfo bmi : bmpSingleton.bmInfos.values())
          {
              bmi.finalBm = null;
              bmi.booted = true;
  
              /*possible issue with >weld< based servers:
              if #getBeanManager gets called in a custom AfterDeploymentValidation observer >after< this observer,
              the wrong bean-manager might get stored (not deterministic due to the unspecified order of observers).
              finally a bean-manager for a single bda will be stored and returned (which isn't the bm exposed via jndi).*/
          }
      }
docs: By cleaning the final BeanManager map after the Deployment got Validated,
  we prevent premature loading of information from JNDI in cases where the
  container might not be fully setup yet.
  
  This might happen if someone uses the BeanManagerProvider during Extension
  startup.