Process instances in Spring are loaded using the application context, not the command context. This can cause OptimisticLockingExceptions if the process instance was modified elsewhere, as this context is not cleared in between invocations.
Using the command-scoped context will make sure that process instance changes between invocations are picked up at the beginning and don't cause a commit exception at the end.