Are you talking about success or rollback cases?  In success cases, as discussed in meeting, I think the correct solution is to actually not delay the afterCompletion processing.  It is only the rollback cases (which include time outs) that cause concurrency issues (from concurrent modification of the collections maintained in the session/pc).  So tbh I don't see how this last one is really a problem for us.