It shouldn't track the way it does, and it certainly shouldn't track HTTPS. It is not even an issue of privacy, it is simple courtesy and common sense.
Or make the +1 a two-gesture event: click the extension button (which is when "tracking" occurs) which opens a balloon, then click a +1 button within the balloon.
Granted, it doesn't know if the visitor has friends that shared it. It still doesn't excuse them for sending all url's.
Facebook received a lot of flack for doing this and I don't see why Google should be excused for this intentional "gaffe".
I have to wonder if this is an unintended side effect of the recent push to have site move to HTTPS - it used to be that HTTPS requests were mostly unique to a user, but now lots of "regular" pages are being requested using HTTP and if you want to make any kind of extension that return data about pages (+1, anti-phishing, etc) you're probably going to to want to send HTTPS URLS as well.
Additionally, these extensions take up minimal space in Chrome. The screen real estate each one gets is the same size as the settings (wrench) icon. Sure, you could fill up your browser UI space with them, but it's much more difficult than it is with IE and there are more hoops to jump through in order to get them there. IE users were (are?) plagued by toolbars because they can be installed externally from the application. As far as I know, Chrome extensions can only be installed from within the application after several prompts and confirmations.