Trace context does not propagate to the callback of ThreadPoolTaskExecutor/Scheduler

TracedThreadPoolTaskExecutor tracedExecutor = new TracedThreadPoolTaskExecutor(myExecutor, GlobalTracer.get());
try (Scope scope = GlobalTracer.activateSpan(span)) {
    ListenableFuture<?> future = tracedExecutor.submitListenable(() -> {
        Thread.sleep(1000); // Let callback run in other thread
        System.out.println(GlobalTracer.get().activeSpan()); // It's OK
    });
    future.addCallback(
        r -> System.out.println(GlobalTracer.get().activeSpan()), // Context loss!
        e -> {}
    );
}

This is confusing me, the context (activeSpan) is missed in the callback while the main task can get it correctly.

Start with TracedThreadPoolTaskExecutor and the submitListenable callback path, comparing how the task and callback obtain their tracing context. Use the supplied Java example to reproduce the missing activeSpan in the success and failure callbacks. Done means the callback observes the expected trace context as the main task does.