looks like it is caused by task clean up listener
this.ksession.addEventListener( new TaskCleanUpProcessEventListener( admin ));
most likely when it is not registered the problem will disappear. Anyway that's certainly a bug, could you please file an jira issue for this?
And that does not happen on successful completion of the process instance?
HTH