Is this a bug that should be reported ?

I would say yes. It is at the very least unexpected behaviour and should therefore be documented if not fixed outright. It might well be a symptom of some deeper as-yet-unknown problem so the Test::Harness maintainers should definitely be informed.

If you can supply a reproducible test case then no doubt others could test and determine if it is indeed an MSWin32-only issue.