Found out this issue while trying to use the new @ImplicitWaitTimeout in a test with a "long running" action such as publishing a new page. Here's the relevant code

app.hitAction("Publish");
assertTrue(app.activationStatusToBe("foobar", PUBLISHED));

Despite an ImplicitWaitTimeout of 60 seconds the assertion (which internally uses webDriver.findElement(locator)) would fail after ~10s.
Debugging showed that ImplicitWaitTimeout is sometimes dropped at several spots in the new UI framework (see Utils.failFastFindElement(..)) but never set again to its previous value, as set by the annotation. This causes an erratic and puzzling behaviour.