A screenshot is not good enough to determine any problem/bug/error or misconfiguration. I trust your description, no need to reinforce with the screen capture. What is needed to see what is going on is a capture of the manager events when that happens. You can capture such a log in this way:
service fop2 stop
cd /usr/local/fop2
script capture.log
./fop2_server -X 1
(log into fop2, call a conference, make that problem happens until you see the stuck conference)
ctrl-C
exit
service fop2 start
At that point you will have a capture.log file with all the manager events that lead to that inconsistent state, that log will show what is happening and if it is because a FOP2 bug, an Asterisk bug, a misconfiguration, etc.. You can send me that log privately so I can take a look at it.