JSR-352 within OSGi EJB or WAR failes to execute batch job

Hi all!

Since a couple of days I'm trying to get JSR-352 to work within of an OSGI War or Ejb in Glassfish 4.1, but it fails on the on the most important part. The execution of the batch job itself.
I'm not sure whether it is a issue of Glassfish or the reference implementation itself, but the BatchRuntime (JobOperator) outputs it would and did execute the job but the actual Batchlet never gets called. I checked this by including a logging statement within the batchlet process method and to be sure I event placed code to create a temp file but both never happend.
If I deploy the war package as simple webapplication everything works as it should do.

Attatched you will find a simple OSGi WAB project. if you placed it under domain/autodeploy/bundles the package gets installed and started and the job itselfs seems to be executed by the batch runtime, but like i mention nothing of the Batchlet implementation will be executed.

I tried to trace the probleme and noticed by setting the "com.ibm.jbatch"-Logger to finest, that the execution stops or more like 'disappears' when the BatchWorkUnit.class should be execution.

I think the project is correct configured. Everything but the batch runtime works. Maybe someone can reproduced this probleme with the attatched war-file.

This is what I did:
- first I registered the "com.ibm.jbatch" logger and set it to finest via the admin gui.
- then to test I deployed the war as a nomal web application and looked whether the expected console output would get printed out.
- afterwards I undeployed the web application and installed the package as osgi bundle by copying the package the {domain}/autodeploy/bundles. The bundle gets installed and started without any errors and the ejb gets registered as OSGi service. The singleton bean gets called and the batch runtime executes the job.xml, but the expected output in the console never gets printed.

What do I miss or is this a bug ?
I don't know, should I report this as bug ? And if so, to which bugtracker should I report this issue? The one of Glassfish or the one of the JSR352 reference implementation of javaee ?

Thanks in advanced.