The issue affects the HTTP layer of Quarkus REST. When writing a response, the framework waits for previously sent response chunks to be fully transmitted before continuing. If the client connection is dropped during this wait, the associated worker thread is never released and remains permanently blocked. Under repeated occurrences, this can exhaust the worker thread pool, resulting in severe performance degradation or complete application unavailability.