I have the same problem with this remote. It's annoying, for example, when I want to skip ahead 3 minutes, and find that the 3 button has inadvertantly registered twice or even three times, so I end up skipping ahead 33 minutes or more.
I think it's a design problem related to 'switch bounce' and as such there's nothing that can be done about it, hardware-wise. But perhaps someone may be able to advise on whether it would be possible to write a script that would prevent a keypress from being recognised within a certain time (eg. 100ms) of another keypress
