Great, thanks for confirming. As I understand it, this is the same behaviour found in watchOS 2, albeit a bit buggier due to the in-development nature of watchOS 3?
Have to say, this was my biggest gripe with watchOS 2 and it baffles me that this isn't in there by default, so I'm disappointed Apple haven't included it in watchOS 3!