There are cases where it would make sense to have a finally block similar in functionality to the C# and Java keyword purpose. There are enough times where I have to duplicate code to clean up resources or revert screen items to a non-processing state that I feel it is necessary for cleanliness and maintainability.
For example, if I disable a control on the screen during some processing, I have to ensure that I reenable that control (the variable it's bound to) and refresh the control at BOTH the end of the screen action AND at the end of the exception handler.
A 'Finally' action flow on the screen would clean this up quite a bit.
The following should explain what I mean a bit better:
Start ---> End
Exception ---> End
Finally ---> End