The only way to be certain is to downgrade to 1.03 and see if it still happens. If it happens in 2.0b3 consistently, and never in 1.03 consistently, then it is definitely a software bug.