I tried the workarounds suggested above, but it looks like the priority annotation is not being respected (I also tried @Order, since it looks like spring-jersey pulls in pre-4.1 spring versions):
INFO: Spring WebApplicationInitializers detected on classpath: [org.glassfish.jersey.server.spring.SpringWebApplicationInitializer@49357096, com.openx.tq.adquality.cbir.gateway.SpringApplicationInitializer@5372ad66]
Dec 29, 2015 6:55:02 PM org.apache.catalina.core.ApplicationContext log
INFO: Initializing Spring root WebApplicationContext
Dec 29, 2015 6:55:03 PM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener
org.springframework.beans.factory.BeanDefinitionStoreException: IOException parsing XML document from class path resource [applicationContext.xml]; nested exception is java.io.FileNotFoundException: class path resource [applicationContext.xml] cannot be opened because it does not exist
I still need to try the workaround suggested by @kknd22 ... but it would be nice to know why the jersey folks don't feel this is an issue - why in the world would you force the use of an xml based configuration in a framework designed to support a spec (JAX-RS) where the whole point of the framework is to avoid xml configuration in favor of annotation based configuration?
The logic of the design choice (including the obvious rejection of the idea that this issue is a genuine bug, considering the years this issue has sat around) is bizarre to say the least.
It should be noted that I'd actually prefer to use as little spring as possible, and generally prefer solutions that hew closer to java standards, but this bug may force me away from jersey and back into springs web framework sigh.