SiteWide Error handler behavior

I am trying to troubleshoot some strange behavior we have noticed with our sitewide error handler and I'm hoping that somebody out there might have some insight as to the best way to deal with it.

We have several CF websites on W2k servers running CF 5 and we use the sitewide error handler to handle the errors on all of the sites on the server. If there is an error in the requested template, or if there are errors in both, the requested template and the applicaion.cfm files then everything works as it should, but if there is an error in the application.cfm only then we see some strange behavior.

What happens is that the sitewide error handler will execute properly, but then the CF server continues on to process the requested template, and if the error in the application.cfm does not directly cause an error in the requested template it will process normally and will be displayed beneath the output of the sitewide error handler as if it was included.

Viewing the source reveals that there are two sets of HTML, Head, and Body tags. Which seems to indicate that both pages are being completely processed, but they are both returned to the browser when only the errorhandler output should be.

Has anyone experienced this or can explain why it is happening?

Also any suggestions on how to make it work correctly would be appreciated.

Afraid I have no idea what could cause that, never seen such behavior before. But then, I rarely use Application.cfm...most frameworks such as Fusebox or Mach-II allow for similar behavior as a part of the framework. If no one else has any ideas, you might try posting this to the CF support forums at Macromedia.

Thanks, I actually do have another message over there already

Would you agree that the expected behavior would be for execution to stop once the sitewide error handler got done processing the error that occurred in the application.cfm?