ActionScript 3.0 :: Error Checking For AddEventListener?

The problem I've found that I keep having and that is pretty recurring between a few of my classes is that several classes use addEventListeners for complete events on loaders, tweens, etc. The question I have is, how do I catch those events in the event that the instantiated class object is removed from the swf file? Because the eventListener keeps listening, for some reason(I assume the object is removed from the stage but garbage collector doesn't get it right away).

My current, most prominent example is this:I have a photo album that utilizes php to import filepaths on the server. There are basically 2 stages: one screen where all the albums are displayed, and another screen where all the images for a given selected album are displayed.

The problem is that when you click one of the albums, it loads all the images from that album and THEN transitions to the viewing page. This is good because it doesn't load all the images from all the albums.
The problem is, it's possible for the user to click one album, and really quickly, before the "album" page fades out, click another album.

If I've managed to not twist your brain inside out with this poor explanation, you may see that the loader object for the previously clicked "album" button will still be loading the one of the previous images. So, when the complete event for the loader is fired, I get this:

Error #2044: Unhandled IOErrorEvent:. text=Error #2124: Loaded file is an unknown type.

Which I assume, obviously, is 2 separate error events. I'm already using error catching that's working for another purpose, but I just can't catch these ones no matter where I put my catch statements. Any help?
Here's the code:

Code:
function clickHandler(event:MouseEvent):void
{
//////some stuff here
////////preps album images for display

[code]....

The first type error gets caught. It loops back through and works fine when you only click one button at a time, but otherwise it freaks out. I just don't know where to put the catch statement so that it just shuts up...