Because conversations are not unlocked in a finally-block exceptions might cause the JSF lifecycle to be exited before the conversation has been unlocked which will lead to failure in acquiring the conversation lock when the user refreshes the browser or otherwise retries the operation.