The problem occurs that way:
We close all Firebirds connections at once but one specified firebird.exe PID connection hangs in this process (firebird-that_hangs.DMP). When this occurs the firebird.exe PID remains in memory and hangs all other firebird attempts access - to close connections, open new connections etc.
When this occurs, the symptom is other firebird.exe PID with high CPU consumption waiting (firebird-waiting.DMP) . If I kill the Firebird PID that hangs the Firebird became normal and "unhang".