In SQL Server 2005, what happens when the plan cache fills up? I have done some research, and from bits and pieces gathered it seems that cached plans are given an "age" that consists of it's weight, or cost to compile, multiplied by the number of times it has been run since being cached. Over time this age is decremented, until it reaches 0, when it is considered "aged out" and is a candidate for flushing when needed. When the plan cache fills, aged out plans are flushed from the cache.
Is there anything else that is happening behind the scenes to complicate this scenario?