Currently you cant supply custom quartz.properties for scheduler binding. The default quartz.properties in org.quartz-scheduler.quartz is loaded even if you provide your custom properties in your sy module as a resource on org/quartz/quartz.properties path.
See forum reference for more info as there may be additional problems when enabling quartz persistence/clustering.