Yeah, it's a known bug -- the Reader doesn't really have it's own clock, apparently, but rather pulls the info from the PC. It can keep track of it on its own for a few days, but then it falls back to '06. It seemed to get better after the first firmware update, but I've noticed it seems to happen more quickly since the second one.
I mostly ignore it.
