Description of problem:
If a lifecycle method of EJB's throw an Exception it is expected that this will be logged and the invocation fail.
This works correct if there is no CDI involved in this deployment.
If a beans.xml is added the Exception is swallowed and the instance might work not correct.



How reproducible:
----- Class ----
@Singleton
@Startup
public class StartupSingletonBean {
  private static final Logger log = Logger.getLogger(StartupSingletonBean.class);

  @PostConstruct
  private void postConstruct() {
    log.info("StartupSingleton is started. Resource 'myString' is '" + myString + "'");
    throw new RuntimeException("THIS IS A TEST");
  }
}



Steps to Reproduce:
1. If the application does not contain a beans.xml the Exception is logged and the Bean is not created.
2. If the application contains a beans.xml the weld deployment is activated and the Exception is swallowed.