DueBy Time set incorrectly by one hour plus or minus when edited across US Daylight Savings time change

There a problem with the programming code for the time on the DueBy field that is either automatically adjusting (or possibly failing to adjust) to correct for Daylight Savings changes. I noticed it because I have several requests that I set last week before the US time change on Sunday Nov 3. I set them to 17:00 (5 pm) on various dates in November and December but now they are all displaying the due time as 4 pm.

Here is a scenario to reproduce this problem on any existing request in a US time zone that adjusts for Daylight Savings:

Set the due date and time to 17:00 March 10 2014 (which should be 5 pm).

After saving, date and time will be displayed as 6 pm.

This result is that the due time is not accurate. A due time setting of 5 pm should be absolute, regardless of whether it will take place in Daylight Savings Time or Standard Time. This is happening for any changes that cross in or out of Daylight Savings time. I had noticed this in the past year or so and was surprised not to find any previous forum topics on this issue.

Now that we have passed this year's "fall back" date, the next window of opportunity for this annoyance is next year's "spring forward" date (Sunday March 9, 2014). That's four months from now. Would it be possible to get this corrected and included in a hotfix before then?