// if this is an observer method for container lifecycle event, it must not inject anything besides BeanManager
if (containerLifecycleObserverMethod && !parameter.isAnnotationPresent(Observes.class) && !BeanManager.class.equals(parameter.getBaseType())) {
throw new DefinitionException(INVALID_INJECTION_POINT, this);
}

which make sense when looking at the infinispan org.infinispan.cdi.InfinispanExtension :

the only thing a portable application may inject into an observer method defined on a CDI extension is BeanManager. However, this rule was not enforced in Weld in the past and it was technically possible to inject other beans in late bootstrap phases (e.g. AfterDeploymentValidation). Since CDI 1.0 does not provide an event that would allow application components to initialize after the CDI implementation is fully initialized, developers tend to misuse injection into extension observer methods (which is by spec non-portable as the container is not fully initialized yet).

This has been identified as CDI-109 and is planned to be addressed in CDI 1.1. You are seeing this issue because Weld 2.0.0.Alpha1 (which I believe you are using) already implements this logic.