Locking remains after program crashes

Our Visual Basic applications access Informix 7 database. One problem we experience is once the client application crashed or network connection is cut, the remaining transaction and locked rows will stay locked. We have to manually kill these locking processes. Otherwise they will stay there forever. Is this normal? I think the transaction or lock should rollback after hardware or system crashes. Does anybody has same experience? Thanks