In general, people using words they don't understand, presumably to sound smart, drives me up a tree. In specific, I wish against reason that more people knew how time zones worked. Microsoft's Raymond Chen agrees:

One way of sounding official is to give the times during which the outage will take place is a very formal manner. "The servers will be unavailable on Saturday, March 17, 2012 from 1:00 AM to 9:00 AM Pacific Standard Time."

Did you notice something funny about that announcement?

On March 17, 2012, most of the United States will not be on Standard Time. They will be on Daylight Time. (The switchover takes place this weekend.)

Now, I'm one of the few people in the world who has implemented a complete time zone package for Windows systems, and regular readers will already know about my vocal defense of the Olson/IANA time zone database. So I don't expect most people to know the ins and outs of time zone abbreviations. But this is the point Chen makes, and I would like to make: if you don't know what you're writing, don't write it. Say "Central time" or "local Chicago time" instead of "Central Standard Time," if for no other reason than you'll be wrong about the latter 8 months out of the year.