[Java] Netty memory release

### Describe the bug, including details regarding any error messages, version, and platform.

Since when we use netty as my memory allocator manager, I found that direct memory is not released after vector is closed.
```
Field field = new Field("test", FieldType.nullable(new ArrowType.Utf8()), null);
RootAllocator allocator = new RootAllocator(Long.MAX_VALUE);
FieldVector vector = field.createVector(allocator);
for (int i = 0; i < 100000; i++){
((VarCharVector)vector).setSafe(i, "test".getBytes(StandardCharsets.UTF_8));
}

System.out.println("before close memory: " + usedDirectMemory() + " bytes"); //before close memory: 4194304 bytes
vector.close();
allocator.close();
System.out.println("after closed memory: " + usedDirectMemory() + " bytes"); //after closed memory: 4194304 bytes
```
I can address the problem that if the inner allocator `PooledByteBufAllocator` won't free the memory chunk , I am not sure if this is expected.

### Component(s)

Java

Comienza con la reproducción en Java proporcionada usando RootAllocator, VarCharVector y PooledByteBufAllocator; después, sigue el comportamiento de cierre del allocator y la gestión de memoria directa de Netty. Confirma si los 4194304 bytes restantes son una fuga real o un comportamiento de pooling esperado, y documenta o prueba el comportamiento esperado resultante.

Escrito por el modelo de indexación a partir del texto del issue.