Is there a specific reason why update is always called on a controller even if active is set to false?  I know the typical way to deal with this is to check for the active state and then return, but it seems silly that this isn't handled internally for the controller.  Seems redundant to me to have to add a check in all my controllers for this.

Sounds like a reasonable suggestion. Only thing I could think of is if a controller needs to clean something up if it is not active… although I can't think of any specific examples when this would be the case.

I might go ahead and make this change this evening if no one has any negative criticism of it?