In the seam 2.0.0.Beta 1 dvdstore example, which uses jbpm, one of the admin pages lists all the tasks assigned to the group of the admin, allowing the admin to assign one of the tasks to him or herself. In this page, a task represents an order placed in the store.
Each time a new order is placed in the store, the number of tasks on that admin page goes up by one, as would be expected. However, the number of queries used render the page of tasks goes up by 4 each time a new order is placed.
This seems bad. I asked about this in the seam forum, and got this back from Gavin:
AFAIK, this is a jBPM question, not a Seam question, unless you have evidence otherwise.
It is not a known issue afaik. You could very easily analyse the jbpm source code and try helping out finding the cause. After which we could have a 'better way'