Unexpected behavior for "No time zone conversion" option

When creating a datestamp field with the "No time zone conversion" option flagged I discovered a strange behavior. When you create a datestamp field with this setting flagged I would expect that no time zone manipulation would occur. However, it seems that if a users time zone is set then this takes precedence over the sites time zone setting. This appears to be happening because if $field['settings']['tz_handling'] is set to 'none' then it calls date_now() within date_now() a new DateObject is created and within the DateObject constructor date_default_timezone_object() is called. This function returns the current date for the current user which is in fact taking into account time zone conversion which to me is an unexpected behavior.

I propose a rework of this behavior to purely return the current date. I've already started work on a patch and will post it as soon as I have something that works.