To release or not to release? autorelease duh!

Well, it turns out that the standard class methods used to instantiate a new NSException object, send an autorelease message to the object, effectively putting it on the nearest NSAutoreleasePool. As with my earlier issue with the cost of the try/catch block, I was mis-informed :-| ... mind you, I have yet to see any official document clearly stating the memory whereabouts of an exception ...