Unclear, it is, yes :) Basically you have a chicken-egg problem. When StatusScheduleController.create is called, there is no application context active (yet), so you can't inject the StatusScheduleProcessor. Make the processor STATELESS and it should work. Btw, the safer way to do stuff only once at Seam app start up is to write an @Observer for org.jboss.seam.postInitialization.
What do you mean by 'conversation scoped context'? I don't see anything conversation related in your code.