Recently my team discovered some nastiness with unhandled exceptions inside our custom SharePoint code. Specifically we found that unhandled exceptions inside of SharePoint.Publishing.LoginRunningOperationJob can result an IIS Application Pool crash.
The reason is because this class puts the delegate code onto a separate thread that when aborted can leave the Application Pool in an unstable state. Which can (and does) result in an Application Pool recycle (which is bad for very large SharePoint sites that take a few minutes to spin-up).
So you need to make sure that your delegate code is wrapped in try/catch and do NOT throw the error from inside your catch (same as unhandled exception).
