Disable pool member when using HTTP/1.1

    Ok. I will try to explain it better.
    First of all: we don´t use persistence ( I´m talking about cookie persistence or something related to that. We don´t need that each client goes to the same pool member).
    We do want to use HTTP/1.1 from the client to the pool members (I want to send a lot of requests thru the same connection). 
    In this context, we need to do clean deploys in the pool members without loosing requests.
    To do a deploy in a pool member we have tried:
    1) Put the member disabled and then stop de member´s webserver
    2) Put the member in "forced offline" and then stop the member´s webserver
    3) Remove the member from the pool and then stop the member´s webserver

    In the three options, we have noticed that new requests were still coming to the member thru the active connections that it has with the virtualserver, so when we stop the members´s webserver, we lost some requests.

I want that new requests go only to active pool members in a HTTP/1.1 environment.
If I disabled or forced offline a pool member, I don´t want that requests were still coming to it thru the active connections.
I don´t know if this is possible. 
If LB::detach causes that from the virtualserver to the pool members each new request will generate a new connection (HTTP/1.0 environment), that`s not an option.

I hope yo can understand me now. And sorry for my bad english.
Thanks!