Yeah. That just seems like a hack though which I'd prefer to avoid if possible. DST, though I agree is an archaic concept, and a terrible pain to program for, affects over 1 billion people. Computer platforms should be able to "just work" with it.
I'm 99% sure this is a platform issue. When I rerun my stuff today to create a new call to schedule() all is well. It's just when I am scheduling the next run (for today) yesterday (when DST was still in effect) that it broke. Unfortunately, HE doesn't seem to give me any good way to mess with DST for testing so I really won't even know if it's fixed until March when DST begins again 
