We have used the test script provided in the link http://seclists.org/fulldisclosure/2011/Aug/175 to test this vulnerability. We ran with 50 child processes and memory went up to 200 MB and it's not coming down also. But there is no Apache crash observed with this test result.

The vulnerability is not dependent on the presence or absence of the module mod_deflate. This is clear from the apache mail archive link. RVM does not use the module mod_deflate.
We have tested the mitigation options provided by IBM and as well as apache.

Mitigations:
=========
1) Use SetEnvIf or mod_rewrite to detect a large number of ranges and then either ignore the Range: header or reject the request.
We recommed to use mod_rewrite option to reject request if range exceeds 'n' number of bytes. We tested with SetEnvif and found that it is not restricting the ranges. The number of bytes to restrict is varying from IBM and apache. Any specific value can be given to restrict the range header, still it would be better to follow the apache way. Apache suggested a number of 5 bytes to restrict.
steps to configure:
a) In the httpd.conf, add the following lines in the virtual host section.

1. Reject request when more than 5 ranges in the Range: header.
2. CVE-2011-3192
   #
   

   RewriteEngine on

   RewriteCond %{HTTP:range} !(^bytes=[^,]+(,[^,]+){0,4}$|^$)

   RewriteRule .* - [F]
   

   
   
    

   b)     In the httpd.conf enable the module "rewrite_module" to support the above directive.

   To do this find the line,

   #LoadModule rewrite_module modules/mod_rewrite.so

   and remove # from the line.

   
   We have tested with the above workaround. In case of exceeding its range header apache returns forbidden error (403).