I just encountered this problem with a Credit Card expiration date field yesterday. I'd stupidly changed 00/0000 as input mask to 00/00, and encountered the problem you're having. the issue is that if the second pair of digits is a valid date, it will be interpreted as a date and the current year will be supplied tacitly. Thus, if you enter:
06/09
for Jun 2009, it will be stored as:
06/09/2009
On the other hand, if you enter:
06/34
it will be interpreted as
06/01/1934
So far as I can see, the only way for you to do what you want is to use a 4-digit year.