MP Context ThreadContext isn't propagated properly with @RequestScoped

Describe the bug

The ThreadContext from MP doesn’t reliably capture the context of beans that include a @RequestScoped bean.

Not sure if I’m missing something, but the example (that I’ve tested with other MP impls) described here doesn’t work with Quarkus.

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

@ApplicationScoped
@Path("contexts/example")
public class ThreadContextExampleResource {

    @Inject
    ExampleStore exampleStore;

    @Inject
    ThreadContext threadContext;

    @Inject
    ManagedExecutor mes;

    @Inject
    Notifier notifier;

    @PUT
    public void setExample(String example) {
        exampleStore.setExample(example);
        mes.execute(threadContext.contextualRunnable(notifier::notifyAbout));
    }
}

@RequestScoped
class ExampleStore {

    private String example;

    public String getExample() {
        return example;
    }

    public void setExample(String example) {
        this.example = example;
    }
}

@Dependent
class Notifier {

    @Inject
    ExampleStore exampleStore;

    public void notifyAbout() {
        LockSupport.parkNanos(200_000_000L);
        System.out.println("New example: " + exampleStore.getExample());
    }
}

Invoking curl localhost:8080/contexts/example -i -XPUT -H 'Content-Type: text/plain' -d 'foobar' produces empty logs, if the processing takes longer (our wait for 200ms):

New example: null

Output of uname -a or ver

No response

Output of java -version

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

2.0.2.Final

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

It didn’t make a difference whether the ThreadContext or ManagedExecutor were obtained programmatically or via injection.

[gsmet]

@sdaschner could you check if this is still an issue with latest Quarkus? A lot of changes have been made in this area.

[quarkus-bot[bot]]

/cc @FroMage, @manovotn