Hi J W,
I don’t think these applications are intended to be the ubiquitous jbpm/drool runtime engine, at least not at the current time. I believe their purpose is to show case what is possible to achieve with the framework.
As you said, when you have business process with Rules Tasks you need to be able to create a knowledge session per request. These ksession will persist/serialized the rule-facts to be evaluated inside the Rules Tasks components. So don’t create static ksessions in your configuration file. I would suggest you create your own war file that exposes your services and per invocation you dynamically create a ksession (using the framework api). The out of the box persistence mechanism should take care of the rest.