Fine line to walk, isn't it? Taking ownership of your code would seem to be pretty closely related to taking pride in your work, and the motivations that entails. Having worked with and for $BIG_COMPANIES I would have to agree with your observation that the majority of developers are not, uh, enjoying a personal association with the fruits of their labour, and it shows.

Maybe own it till you're proud of it, then let it go! Schedules don't always allow every codule to be the shining star in your portfolio, but there should maybe be pride to be had in a really dirty hack done on an insane deadline ^_^