Quartz configuration ignored with WAR deployment

1. install nuxeo 8.10
2. configure nuxeo with PostgreSQL and clustering
3. ensure quartz is started properly :

   2017-10-17 11:04:51,342 INFO  [localhost-startStop-1] [org.quartz.impl.StdSchedulerFactory] Using default implementation for ThreadExecutor
   2017-10-17 11:04:51,357 INFO  [localhost-startStop-1] [org.quartz.core.SchedulerSignalerImpl] Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
   2017-10-17 11:04:51,357 INFO  [localhost-startStop-1] [org.quartz.core.QuartzScheduler] Quartz Scheduler v.2.2.3 created.
   2017-10-17 11:04:51,359 INFO  [localhost-startStop-1] [org.quartz.impl.jdbcjobstore.JobStoreCMT] Using db table-based data access locking (synchronization).
   2017-10-17 11:04:51,361 INFO  [localhost-startStop-1] [org.quartz.impl.jdbcjobstore.JobStoreCMT] JobStoreCMT initialized.
   2017-10-17 11:04:51,361 INFO  [localhost-startStop-1] [org.quartz.core.QuartzScheduler] Scheduler meta-data: Quartz Scheduler (v2.2.3) 'Quartz' with instanceId 'frantzmbp.local1508231091346'
     Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
     NOT STARTED.
     Currently in standby mode.
     Number of jobs executed: 0
     Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 1 threads.
     Using job-store 'org.quartz.impl.jdbcjobstore.JobStoreCMT' - which supports persistence. and is clustered.
   
   2017-10-17 11:04:51,361 INFO  [localhost-startStop-1] [org.quartz.impl.StdSchedulerFactory] Quartz scheduler 'Quartz' initialized from an externally opened InputStream.
   2017-10-17 11:04:51,362 INFO  [localhost-startStop-1] [org.quartz.impl.StdSchedulerFactory] Quartz scheduler version: 2.2.3
   

4. create a WAR app:

   ./nuxeoctl pack /tmp/mynuxeo.war
   

5. deploy it into Tomcat 7
6. start Tomcat
7. observe the following in the logs:

   2017-10-17 12:03:55,899 INFO  [localhost-startStop-1] [org.quartz.impl.StdSchedulerFactory] Using default implementation for ThreadExecutor
   2017-10-17 12:03:55,916 INFO  [localhost-startStop-1] [org.quartz.core.SchedulerSignalerImpl] Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
   2017-10-17 12:03:55,916 INFO  [localhost-startStop-1] [org.quartz.core.QuartzScheduler] Quartz Scheduler v.2.2.3 created.
   2017-10-17 12:03:55,917 INFO  [localhost-startStop-1] [org.quartz.simpl.RAMJobStore] RAMJobStore initialized.
   2017-10-17 12:03:55,918 INFO  [localhost-startStop-1] [org.quartz.core.QuartzScheduler] Scheduler meta-data: Quartz Scheduler (v2.2.3) 'Quartz' with instanceId 'NON_CLUSTERED'
     Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
     NOT STARTED.
     Currently in standby mode.
     Number of jobs executed: 0
     Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 1 threads.
     Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.
   
   2017-10-17 12:03:55,918 INFO  [localhost-startStop-1] [org.quartz.impl.StdSchedulerFactory] Quartz scheduler 'Quartz' initialized from an externally provided properties instance.
   2017-10-17 12:03:55,918 INFO  [localhost-startStop-1] [org.quartz.impl.StdSchedulerFactory] Quartz scheduler version: 2.2.3
   

quartz.properties is deployed in WEB-INF. Trying to deploy it into WEB-INF/classes does not improve the situation.