By default ASP.NET 2.0 Themes include all Style Sheets found within the active Theme directory into the HEAD of the document. This severely limits many CSS features and in many cases makes things more difficult then they have to be. Read more here: The Problems with Themes, Skins, and Cascading Style Sheets (CSS) - Where it all Falls Apart. One of my favorite solutions to this problem is to use the VirtualPathProvider (VPP) to exclude all the StyleSheets from auto inclusion (or selectively include a single StyleSheet like Import.css). Read more about the VPP here: A Resolution to The Problems with Themes, Skins, and Cascading Style Sheets (CSS) - Putting the Cascades back into ASP.NET 2.0 Themes (taking control over CSS Cascades / Load Order, Media Types, and Overrides).
In your case you may want to use the VPP, then place a ContentPlaceHolder within the HEAD of your page - this would allow you to load your Style Sheets on a per page basis.
I was able to answer my own question.
The answer is Global Themes and you can find info about them here...