Strange use of 'META-INF' in Spring Batch Admin

Spring Batch Admin expects our context files for jobs and overrides to be the classpath under /META-INF/spring/batch/* and in the spring-batch-admin-sample project there is a META-INF folder under src/main/resources. So, what actually happens is that this gets copied into the WAR at WEB-INF/classes/META-INF, which means this isn't *the* META-INF folder for the WAR, in the J2EE sense, it's just a folder that happens to be called META-INF but could have been called anything.

So, my question is, why use a folder called META-INF? It seems confusing to me - indeed, in my project we've got our batch config files in the *real* META-INF folder at the root of the WAR, and this happens to work on Websphere but not in JBoss or Glassfish which (presumably) take a stronger approach on isolating modules' classpaths.