I'm sorry this is not supported. You could try to exclude the Weld ServletContainerInitializer from scanning by means of
<absolute-ordering>(if necessary, i.e. if your container supports the ServletContainerInitializer), then register Weld’s listener manually in the
WEB-INF/web.xmland use a custom ServletContextListener to start Spring (declare it before the Weld's
org.jboss.weld.environment.servlet.Listener). See also Servlet containers.